-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: consider the cli install directory when resolving plugins #1838
fix: consider the cli install directory when resolving plugins #1838
Conversation
🦋 Changeset detectedLatest commit: 12d1742 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Coverage report
Test suite run success833 tests passing in 120 suites. Report generated by 🧪jest coverage report action from 12d1742 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please leave a comment to explain why it was added.
Co-authored-by: Jacek Łękawa <[email protected]>
What/Why/How?
There is an issue when running the
npx @redocly/cli preview
command when the@redocly/realm
package is not installed in the project'snode_modules
: it's dependent package cannot be resolved.This happens because the npx installs both the
@redocly/realm
and it's dependency@redocly/openapi-core
into a cache directory (~/.npm/_npx
for mac and linux) but when resolving plugins, only the project directory is considered.This PR adds the package location to the list of directories to resolve the Realm plugins from.
Reference
Testing
Screenshots (optional)
Check yourself
Security